5 matches found
CVE-2021-26956
The CVE-2021-26956 issue affects the Rust xcb crate (pre-2021-02-04). Bytes from an X server can be interpreted as any data type returned by xcb::xproto::GetPropertyReply::value, causing a soundness violation. Reported CVSS data show a base score of 9.8 (CRITICAL) with network attack vector and n...
CVE-2021-26958
CVE-2021-26958 concerns the Rust xcb crate (up to 2021-02-04) with a soundness violation caused by transmuting to the wrong type in xcb::base::cast_event, which can return a reference to an arbitrary type. Multiple connected sources (OSV entries, Red Hat/RH advisory, Nessus plugin) describe an ou...
CVE-2021-26957
CVE-2021-26957 affects the Rust xcb crate; a soundness issue causes an out-of-bounds read in xcb::xproto::change_property(), illustrated by a format=32 T=u8 scenario, with out-of-bounds bytes sent to the X server. The issue is documented across OSV/NVD references (e.g., RUSTSEC-2021-0019). No rem...
CVE-2021-26955
The CVE-2021-26955 issue affects the Rust xcb crate (up to 2021-02-04). Root cause: xcb::xproto::GetAtomNameReply::name() uses std::str::from_utf8_unchecked() on bytes received from an X server without validation, constituting a soundness violation. Documented impacts indicate a potential securit...
CVE-2020-36205
The CVE-2020-36205 entry concerns the Rust xcb crate (through 2020-12-10). The flaw is in base::Error which does not maintain soundness; a public ptr field enables use-after-free or double-free scenarios. Affected component: xcb crate in Rust. Root cause: misuse of a public pointer field in base:...